HyperLib 1997 Winter - Disc 1/HYPERLIB-1997-Winter-CD1.ISO.7z/HYPERLIB-1997-Winter-CD1.ISO/オンラインウェア/COM/Fetch 3.0.1 folder.sit/Fetch 3.0.1 folder/Fetch 3.0.1 Installer/Fetch Help.rsrc/FHLP_500_Troubleshooting

Text File | 1996-03-05 | 8KB | 77 lines

Troubleshooting

When I upload GIF or JPEG files in MacBinary format my web browser canﾕt display them.

Web browsers (and a lot of other software) do not expect to find files encoded in a format like MacBinary II; they expect to find the bare data.  So use Raw Data format for uploading web graphics, or other cross-platform files.

When I try to open a connection I get a -3221 or a -3264 error.

Those are Open Transport errors.  You should make sure that you are running the latest version of Open Transport (1.1 is expected to be released in Spring, 1996, and it will fix many problems with earlier releases).  If that does not help try checking the ﾒDonﾕt make Open Transport callsﾓ box in the Misc. section of Preferences.

Fetch can download files but when I try to upload a file  over my modem connection the computer freezes, or the upload fails.

There is probably a problem with the flow-control settings of your dial-up software or your modem.  Make sure that your modem init string enables hardware handshaking, and that your dial-up software is configured to do hardware handshaking.  Consult your modem manual or service provider for more information.

When I try to open a connection, my computer freezes.

Check the configuration of your SLIP or PPP software, and consult with the administrators of the dial-up service you are using.  This sort of problem is usually caused by misconfiguration of the dial-up software.

When I try to get a file from an IBM MVS server Fetch creates an empty folder.

This is due to a bug in the server (and affects some other servers besides IBMﾕs).  The workaround is to check the ﾒTreat mystery items as filesﾓ box in the Misc. section of Preferences.

I have a 14,400 bps modem, but I only get 1000 bytes/second.

Modems use 10 bits to send a byte, so 1000 bytes/second over a modem translates to 10,000 bps.  In addition to data, your modem must also transmit packet headers, acknowledgements, and other information.  So you should not expect to always get the modemﾕs rated speed in actual data throughput.  If you think that your throughput should be better (e.g. it is less than 80% of the modemﾕs rated speed) you should check your modem init string and the configuration of your dialup software, or check with your network service provider.

Fetch slows down and eventually drops the connection when I transfer a file over my dial-up link.

Check the configuration of your SLIP or PPP software, and consult with the administrators of the dial-up service you are using.  This sort of problem is usually caused by misconfiguration of the dial-up software.

The file list includes other information besides the file name, and the Get File button doesnﾕt work.

Try refreshing the file list by choosing the current directory from the directory pop-up menu; that will usually fix this problem.  Otherwise you can hold down the option key when you press the Get File button and type in the fileﾕs name by hand.

The file list does not include a file that I know was just put there.

Try refreshing the file list by choosing the current directory from the directory pop-up menu; that will usually fix this problem.  Fetch re-uses file lists when they have not changed in a long while, but this makes it possible to miss new changes.

I canﾕt connect to ftp.apple.com with Fetch but I have no problem connecting from a Unix machine.

The server at ftp.apple.com requires that its clients be assigned an official domain name.  Your network administrator may not have assigned names to the addresses used by Macintoshes running MacTCP; that would cause connection attempts from your Mac to fail while a Unix machine succeeds.  Your network administrator can resolve this problem by assigning names to those addresses.

I canﾕt display GIF files that Iﾕve downloaded from vmd.cso.uiuc.edu.

That ftp server has a bug that causes it to send binary files to Fetch in EBCDIC form rather than ASCII.  To work around the problem check the Use ﾒTYPE Iﾓ for binary transfers checkbox in the Miscellaneous section of Preferences.

When I tell Fetch to send the FTP command  ﾒlsﾓ I get an error message about the command  ﾒLSﾓ; why does Fetch capitalize the command?

Fetch does not capitalize the command, the server does.  In fact capitalization of FTP commands does not matter.  The problem is that ﾒlsﾓ is not an FTP command; it is a command used in many command-line FTP clients, such as the standard Unix client, but it is not a part of the FTP protocol.  The corresponding FTP command is ﾒNLSTﾓ.  Similarly, ﾒdirﾓ, ﾒgetﾓ, ﾒputﾓ, and ﾒcdﾓ are not FTP commands; the proper commands are ﾒLISTﾓ, ﾒRETRﾓ, ﾒSTORﾓ, and ﾒCWD.ﾓ

The file names in the file list donﾕt look right -- there is size and date information in the name column.

Fetch sometimes guesses what kind of computer it is talking to, and it can guess incorrectly.  You should be able to correct the problem by refreshing the file list -- choose the current directory from the directory pop-up menu above the file list.

The files I get donﾕt have the right icon.

This problem can be caused by a number of factors.  First be sure that you are using the right settings -- if youﾕve tried the Automatic setting try Binary.  It may also be helpful to read the ﾒAutomatic/Text/Binaryﾓ help topic under ﾒReference.ﾓ  If you are using System 4.2 and Finder 6.0 you should upgrade since that system version has a bug that causes files to lose their icons.  If you use MultiFinder you should try saving the file to a folder that is not currently open in the Finder.  The Finderﾕs Get Info... command sometimes fixes incorrect icons under MultiFinder.  If all else fails send mail to [e-mail].

I can connect to a machine on my local network but not to Internet FTP servers.

Check the Gateway Address section of the MacTCP (or TCP/IP) control panel, and make sure it contains the right address.

I get the message ﾒThis is not a proper BinHex format file.ﾓ

This means that Fetch could not successfully de-binhex the file.  You should try unchecking the BinHex4 Format button in Preferences and downloading again (see the ﾒPreferencesﾓ help topic under ﾒReferenceﾓ).  Then try to de-binhex the file with either BinHex4 or Stuffit!, two Macintosh utilities.  If they succeed please send a note to [e-mail], since this indicates that Fetch has a bug.  Otherwise the problem may be that the BinHex file is incomplete.  If it has other pieces you will have to get them the same way and assemble them on your Macintosh before running BinHex4 or Stuffit!.  Finally, the file may just be corrupted.  In that case contact the source and ask for a new copy.

I get the message ﾒThis is not a proper MacBinary II file.ﾓ

This message, and other ones about MacBinary I, AppleSingle, StuffIt! and MacHost format files, mean that the file has been corrupted in some way.  Contact the source of the file to get a new copy.  If the file was created by Fetch send a report to [e-mail] so we can try to find the bug.

The Stop button doesnﾕt work when Iﾕm connected to a VMS Vax.

We have observed problems with Stop on VMS and CMS systems.  Weﾕre working on these problems and in the meantime you can cancel a transfer by closing the connection altogether.

Fetch canﾕt seem to connect to hosts while NCSA Telnet is running.

Some old versions of NCSA Telnet monopolizes the name-lookup service, so while it is running other programs that use MacTCP (such as Fetch) canﾕt connect to other machines by name.  You can work around the problem by quitting from NCSA Telnet or entering the hostﾕs IP address in the New Connection... dialog box.  Newer versions of NCSA Telnet do not have this problem.